Release 10.1A: OpenEdge Development:
Web Services

Getting a WSDL file

The Web service deployer can make the WSDL for a Web service available in many possible ways, including (but not limited to):

Hosting it with a WSA to which it is deployed using the Web services tools.
Using e-mail to distribute it.
Posting it on a Web server.
Hosting it in a UDDI directory.

While the Web service developer can use any available technique to provide a Web-services-tools-defined WSDL file, they can host the file on a network using a WSA by deploying the Web service using the Web services tools. This deployed WSDL file resides at a URL determined by the WSA installation and other information specified for the Web service at deployment. Once the Web service is deployed, the WSA administrator can make the WSDL available by enabling access to WSDL listings on the network. For more information on Web service deployment, see the Web service chapters of OpenEdge Application Server: Administration .

To obtain a WSDL file deployed to a WSA instance, you can download it over the network through its URL, specified using the following syntax:

Syntax

http[s]://host:port[/web-server-context]/wsa-webapp-context/wsa-instance/ wsdl?targetURI=web-service-name

Note: The syntax is case sensitive.

For example, here is a WSDL retrieval URL for a Web service with the friendly name, OrderInfo, that is deployed to a WSA instance (wsa1) running in the WSA Web application context (wsa):

http://servicehost:80/wsa/wsa1/wsdl?targetURI=OrderInfo

For more information on the syntax of the WSDL retrieval URL, see the chapters on the WSA in OpenEdge Application Server: Administration .

Note: As an aid for developing client code to test Web services under development, the Web service developer can optionally generate a WSDL file from ProxyGen when generating versions of the Web service definition prior to deployment. This file is written to the generation output directory specified in ProxyGen and can be used to create client interface prototypes for reference during test development. For more information, see OpenEdge Development: Open Client Introduction and Programming .